-
-
Notifications
You must be signed in to change notification settings - Fork 11
chore: migrate to tsdown #760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯 thanks!
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #760 +/- ##
=======================================
Coverage 61.00% 61.00%
=======================================
Files 35 35
Lines 2921 2921
Branches 463 463
=======================================
Hits 1782 1782
Misses 1139 1139
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
JoshuaKGoldberg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welp, there are build failures in Node.js 18. ts-api-utils still supports 18 in the current major. We haven't discussed plans to release a new one to breaking-change drop support for Node.js 18. Is this a blocker?
|
This is because rolldown and tsdown do not support bundling in node 18, but his outputs will not be affected. Therefore, we need to find a way to test and run the outputs by tsdown in node18. |
|
👍 if you can figure that out, great! I haven't looked deeply. |
PR Checklist
status: accepting prsOverview
tsup is not actively maintained anymore, migrating to new alternative tsdown.